Function identity and storage network access #228
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The function apps are allocated a subnet in the deployment's vnet, and that vnet is associated with the two storage accounts which the functions communicate with (the host storage account which operates the function, and the image output account). The storage accounts are otherwise restricted from public access. Additionally, access keys were disabled on the storage accounts so the Function App was transitioned to use Managed Identity for accessing hte underlying storage, including during the "remote build".
Two upgrades support this transition: from a Consumption to a Premium App Service Plan and to a more recent version of the Linux Function App.
Builds off of existing PRs:
Supersedes #227
Supersedes #226